Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
CL/SuperSession Started task(s) must be properly defined to the Started Task Table ACID for Top Secret.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-224654 | ZCLST032 | SV-224654r519781_rule | Medium |
| Description |
|---|
| Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data. |
| STIG | Date |
|---|---|
| z/OS CL/SuperSession for TSS Security Technical Implementation Guide | 2021-06-25 |
Details
| Check Text ( C-26337r519779_chk ) |
|---|
| Refer to the following report produced by the TSS Data Collection: - TSSCMDS.RPT(#STC) Automated Analysis Refer to the following report produced by the TSS Data Collection: - PDI(ZCLS0032) Verify that the CL/SuperSession started task(s) is (are) defined in the TSS STC record. |
| Fix Text (F-26325r519780_fix) |
|---|
| The CL/SuperSession system programmer and the IAO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP. A unique ACID must be assigned for the CL/SuperSession started task(s) thru a corresponding STC table entry. The following sample set of commands is shown here as a guideline: TSS ADD(STC) PROCNAME(KLS) ACID(KLS) |